Dynomotion

Group: DynoMotion Message: 4983 From: himykabibble Date: 5/16/2012
Subject: Odd Thing Happened....
I had an odd thing happen today. I was running some G-code that had an error in it. There was a G03, but the preceding line that set the initial position was missing, so the G3 was defining an invalid mode. When the KFlop got to the G3, it simply hung. The interpreter did not stop, it simply went out to lunch. I was able to recover by re-loading the file. Shouldn't the interpreter stop executing in this case, and call the "complete" callback?

Regards,
Ray L.
Group: DynoMotion Message: 4986 From: Tom Kerekes Date: 5/17/2012
Subject: Re: Odd Thing Happened....
Hi Ray,
 
Not exactly sure what you mean.  Probably should generate an error.  Is it repeatable?
 
Regards
TK

Group: DynoMotion Message: 4989 From: himykabibble Date: 5/17/2012
Subject: Re: Odd Thing Happened....
Tom,

Yes, it is repeatable, but it seems to be a problem in my app, as when I run the same code in KMotionCNC, I do get the correct error. I'll have to dig into it a bit.

Regards,
Ray L.

--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Ray,
>  
> Not exactly sure what you mean.  Probably should generate an error.  Is it repeatable?
>  
> Regards
> TK
>
> From: himykabibble <jagboy@...>
> To: DynoMotion@yahoogroups.com
> Sent: Wednesday, May 16, 2012 10:31 PM
> Subject: [DynoMotion] Odd Thing Happened....
>
>
>  
> I had an odd thing happen today. I was running some G-code that had an error in it. There was a G03, but the preceding line that set the initial position was missing, so the G3 was defining an invalid mode. When the KFlop got to the G3, it simply hung. The interpreter did not stop, it simply went out to lunch. I was able to recover by re-loading the file. Shouldn't the interpreter stop executing in this case, and call the "complete" callback?
>
> Regards,
> Ray L.
>